home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Diamond Collection
/
The Diamond Collection (Software Vault)(Digital Impact).ISO
/
cdr37
/
isr100a.zip
/
ISERVER.CFG
< prev
next >
Wrap
Text File
|
1995-02-25
|
4KB
|
122 lines
; iSERVER configuration file.
; -------------------------------------------------------------------------
;
; Addresses that iSERVER should process when handling netmail
;
PROCESS 1:2401/305.999
PROCESS 1:2401/305
;
; Where the netmail *.MSG files are located
;
NETMAIL e:\fd\mail
;
; Update these semaphore files when netmail has been altered
;
UPDATE e:\fd\FDRESCAN.NOW
UPDATE e:\fd\FMRESCAN.NOW
;
; Readdress messages from one address to another. This option is good
; if you want to route messages from one destination to another.
;
XADDRESS 1:1/31 1:2235/10.999
;
; Automated response commands. When a message comes in addressed to
; one of the following names, it either returns a text file, or if
; the filename is a program, preceed it with an astrisk "*" and the
; program will be run, using a REQUEST/RESPONSE drop file method. For
; more information about that, see the documentation. Also, if you
; place a third parameter on a RESPOND command, it replaces the subject
; with that string if posting a response to the sender. (limited to
; 3 RESPOND commands in unregistered mode)
;
RESPOND HELP e:\fd\tosser\HELP.TXT
RESPOND SERVER e:\fd\tosser\SERVER.TXT Automated Response
RESPOND FILESERV *e:\fd\tosser\FILESERV.EXE Your request
;
; When processing messages, ignore any that are addressed to the following.
; This is good for stopping messages from being 'bounced' due to unknown
; users.
;
IGNORE gecho
IGNORE allfix
IGNORE areamgr
IGNORE filemgr
;
; You can also use the IGNORE to keep your own internet mail in the
; netmail editor if you prefer. (remember that when replying you
; must use your netmail AKA listed)
;
IGNORE sysop
IGNORE pete rocca
;
;
; User base location (for checking for valid users) If this list is
; not specified, then all user names will be considered valid.
;
; First parameter Second parameter
; - RA2 (RemoteAccess 2.x) - Path to USERSIDX.BBS
; - ASCII (ASCII text file listing) - Filename of ASCII file
;
USERS RA2 e:\ra\msgbase
;
; Internet posting/tossing information
;
UUCP_ADDRESS 1:2235/10.999
SITE_ADDRESS 1:2401/305.999
SITE_NAME mcc.uti.com
SITE_BASE JAM e:\ra\jammcc\EMAIL
SITE_SERVERNAME server
;
; Log file
;
LOG e:\ra\ISERVER.LOG
;
; If you are using handles for customizable internet names, you can
; run ISERVER /USERID to setup a users handle that is acceptable
; for the internet. It will toggle on a flag of your choice once
; set, so you can make your system only run /USERID if the user
; hasn't yet selected an account name. (Partial names matched)
;
MAX_HANDLE_LENGTH 20
MIN_HANDLE_LENGTH 4
SET_HANDLE_FLAG A1
BAD_HANDLE finger
BAD_HANDLE ftp
BAD_HANDLE gopher
BAD_HANDLE www
BAD_HANDLE admin
BAD_HANDLE root ; note that it takes parts of names
BAD_HANDLE serv ; so listserv, fileserv are also bad
;
; You can restrict certain functions also. The names will not be able
; to be sent to, nor as the first word in the subject. If you follow
; it with a second parameter, then if the user has that flag, then it
; will be allowed, otherwise it will be bounced. (Partial names matched)
;
RESTRICT SUBSC A2
RESTRICT LISTSERV A2
RESTRICT ADD A2
RESTRICT REQUEST A2
RESTRICT WWW A2
RESTRICT ARCHIE A2
RESTRICT GOPHER A2
RESTRICT FILESERV
RESTRICT FTP
RESTRICT GET
;
; By default UUENCODED files are not permitted to be sent. This is to
; minimize costs when using a gateway. However you can allow UUENCODED
; files for certain users, all users, or users with a specific flag.
;
; Examples: ALLOW_UUENCODED pete rocca (allows Pete Rocca to send)
; ALLOW_UUENCODED A2 (allows users with flag A2)
; ALLOW_UUENCODED ALL (allows all users to send)
;
ALLOW_UUENCODED A3
ALLOW_UUENCODED sysop
ALLOW_UUENCODED pete rocca
;
;
REGISTER SERIAL# REGISTRATION#
;